1. Model Introduction
LTX-2 and LTX-2.3 are Lightricks video models for text-to-video and image-conditioned generation. Their defining deployment choice is the pipeline: one-stage minimizes latency, standard two-stage refines quality, and LTX-2.3 adds a 1920×1088 HQ path. Choose LTX when one model family must span fast generation, higher-quality refinement, and LoRA adaptation. Two-stage quality costs substantially more memory and startup work because both DiTs and the spatial upsampler participate; use the one-stage path when latency or capacity matters more than final detail. UseLightricks/LTX-2 or Lightricks/LTX-2.3 as --model-path. SGLang loads the two-stage upsampler and distilled components from the selected snapshot.
2. SGLang-diffusion Installation
Install SGLang with diffusion dependencies:3. Model Deployment
This section provides deployment configurations optimized for different LTX pipelines and hardware targets.3.1 Basic Configuration
The LTX series supports one-stage and two-stage pipelines. LTX-2.3 also supports the HQ two-stage pipeline. The recommended launch configuration depends on whether the target GPU can keep both two-stage DiTs resident. Interactive Command Generator: Use the configuration selector below to generate a deployment command. The default selection targets a single NVIDIA H200 withresident two-stage mode. For multi-GPU serving, start from the 2-GPU or 4-GPU presets and only change parallelism if you need more memory headroom.
3.2 Configuration Tips
Choose the pipeline class based on the quality and latency target:
Feature compatibility:
For two-stage pipelines,
--ltx2-two-stage-device-mode controls transformer residency:
Other deployment flags:
--lora-path: Preload a community LoRA adapter.--lora-weight-name: Select the exact safetensors file when the LoRA repository contains multiple weight files.
For native LTX-2.3 two-stage serving without a user LoRA,
resident is the fastest high-VRAM path. LTX-2 still applies the distilled LoRA during the stage switch, so --ltx2-two-stage-device-mode is mainly an LTX-2.3 optimization. When you pass --lora-path, SGLang still applies the user LoRA during the two-stage switch, so use resident on H200-class GPUs for enough VRAM, but do not expect the same premerged-stage2 benefit as the no-user-LoRA path.3.3 Fast multi-GPU presets
For latency-oriented LTX serving, prefer CFG parallel over sequence parallelism. CFG parallel splits guidance branches across GPUs, while SP/Ulysses is mainly a memory/long-sequence tool for LTX.
Use
--enable-cfg-parallel for degree-2 CFG parallel. Use --cfg-parallel-size only when you explicitly need a different CFG branch count. If resident exceeds available VRAM, keep the same parallelism preset and switch only the device mode to original.
On high-VRAM GPUs, add --text-encoder-cpu-offload false if text encoding latency matters and you have enough memory.
3.3.1 Two GPUs
3.3.2 Four GPUs
4. Model Invocation
4.1 Basic Usage
The examples below spell out the current SGLang sampling defaults for reproducibility:4.1.1 LTX-2 one-stage text-to-video
4.1.2 LTX-2.3 one-stage text-to-video
4.1.3 LTX-2 two-stage text-to-video
4.1.4 LTX-2.3 two-stage text-to-video
4.1.5 LTX-2.3 HQ text-to-video
4.1.6 Image-to-video with one reference image
Pass one image to--image-path for image-conditioned generation:
4.1.7 First-to-last-frame transition with two reference images
Pass two images to--image-path for transition-style TI2V. The first image is used as the starting condition and the second image is used as the ending condition.
4.2 Advanced Usage
4.2.1 Use community LoRAs
Use--lora-path to load a LoRA adapter. If the Hugging Face repo contains multiple safetensors files, use --lora-weight-name to select the exact file. --lora-scale maps to the standard LoRA merge scale and defaults to 1.0.
The following example uses valiantcat/LTX-2.3-Transition-LORA:
Some community LoRAs only include weights for transformer blocks. In that case, SGLang logs a concise coverage summary and leaves unmatched LoRA-capable layers on the base model weights. This is expected when the adapter format intentionally omits those layers.
5. Practical Tips
- Use
--pipeline-class-name LTX2TwoStagePipelineas the default LTX two-stage quality path. - Use
--pipeline-class-name LTX2TwoStageHQPipelinewhen you want the HQ path and have enough VRAM for larger outputs. - Use
--ltx2-two-stage-device-mode residenton high-VRAM GPUs if latency matters more than memory usage. - Use
--ltx2-two-stage-device-mode originalwhen comparing against official two-stage behavior. - Keep
--widthand--heightaligned with the target model resolution; for LTX models, these are output video dimensions.
